Link-node maps based on open area maps

ABSTRACT

Systems and methods for generating and using geographic data are disclosed. For example, one method comprises generating and/or identifying an open area map. A route is generated using the open area map. A path segment record and/or a node record is created based on the generated route. The path segment record and/or the node record may be stored in a geographic database.

REFERENCE TO RELATED APPLICATIONS

The present application is a continuation-in-part of application Ser. No. 12/179,635 filed Jul. 25, 2008 now U.S. Pat. No. 8,099,237, which is related to the copending patent applications filed on the same date, Ser. No. 12/179,668, Ser. No. 12/179,676, Ser. No. 12/179,680, Ser. No. 12/179,692, Ser. No. 12/179,713, and Ser. No. 12/179,726, the entire disclosures of which are incorporated by reference herein.

BACKGROUND OF THE INVENTION

The present invention relates to geographic data and/or navigation and, more particularly, to map structures, such as open area maps, and the use thereof.

As the world population increases, more and more infrastructure, buildings, exterior and interior development, and other features to support human growth are being generated. Also, existing, infrastructure, buildings, parks, and other environments are being adapted to accommodate more people and traffic. The increase and adaptation of environments impact travel and how people go from one place to another.

Navigation systems and/or devices are used to aid travel. For example, vehicle navigation devices may assist a person driving on a road network. Such devices may provide routing and guidance to a desired destination based on existing roads or pathways.

However, there are areas in which people move about that do not have established roads, tracks, or paths. For example, floors of a building, parks, or other exterior or interior areas are treaded upon on a daily basis. People are able to move about in such areas in any number of patterns to get from one place to another. However, some movement or patterns of movement in these areas may be inefficient or unnecessary based on confusion, lack of knowledge of the layout of an area, or other factors. Also, a person may not know how to get from one point to a desired destination in such areas.

SUMMARY OF THE INVENTION

According to one aspect, a method of generating geographic data is provided. The method comprises generating and/or identifying an open area map. A route is generated using the open area map. A path segment record and/or a node record is created based on the generated route. The path segment record and/or the node record may be stored in a geographic database.

The present invention is defined by the following claims, and nothing in this section should be taken as a limitation on those claims. Further aspects and advantages of the invention are discussed below in conjunction with the preferred embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a system for generating an open area map.

FIG. 2 is an image of a layout used in the system of FIG. 1.

FIG. 3 is an image corresponding to a process used in the system of FIG. 1.

FIG. 4 is another image corresponding to another process used in the system of FIG. 1.

FIG. 5 is a diagram illustrating reference regions corresponding to the image of FIG. 2.

FIG. 6 is an image of an open area map generated by the system of FIG. 1.

FIG. 7 is another image of another open area map generated by the system of FIG. 1.

FIG. 8 is a flowchart of a method for generating an open area map.

FIG. 9 is a flowchart showing an example of a step of the method of FIG. 8.

FIG. 10 is a flowchart of a method of routing in an open area map.

FIG. 11 illustrates an exemplary embodiment of an open area map.

FIG. 12 illustrates generated data records based on the open area map of FIG. 11.

FIG. 13 illustrates data record components and an exemplary geographic database.

FIG. 14 illustrates a navigation device and/or system that may use data records, such as the data records or components of FIGS. 12 and 13.

FIG. 15 is a flowchart of an exemplary method of generating geographic data.

FIG. 16 is a flowchart of an exemplary method of routing.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS

FIG. 1 shows one embodiment of a system 100 used for generating one or more open area maps. The system 100 includes, but is not limited to, an image source or sources 104, a network 108, a device 112, a network or connection 120, a database 170, a network 180, and a user device 116. Additional, fewer, or different components may be provided. For example, a proxy server, a name server, a map server, a cache server or cache network, a router, a switch or intelligent switch, a geographic database, additional computers or workstations, administrative components, such as an administrative workstation, a gateway device, a backbone, ports, network connections, and network interfaces may be provided. While the components in FIG. 1 are shown as separate from one another, one or more of these components may be combined.

The image source 104 is a website, an application, a program, a workstation or computer, a file, a memory, a server, a beacon or map beacon, a depository, and/or any other hardware and/or software component or database that can store or include images or data associated with images. Alternatively, the image source 104 is one or more images.

In one embodiment, the image source 104 includes one or more images of a layout. The images are raster or pixel based images, such as a JPEG, Bitmap, Pixmap, Tiff, or other pixel or raster based file format. The images may be raster or pixilated scanned copies of paper or hard layouts. Alternatively, the images may be vector based or vectorized images. Layouts may correspond to real-world areas in which a person, pedestrian, or people walk and/or move about. The layouts may also correspond to future real-world areas that have not been built yet. Alternatively, the layouts may correspond to imaginary locales, settings, or areas.

The layouts may represent an unorganized or unconstrained geographic area. For example, the layout is an area in which a pedestrian is not limited to travel only on a set road or path network. Rather, the pedestrian may walk through public plazas, parks, buildings, corridors, lobbies, or hallways having no associated road or path network or pattern. Additionally, the pedestrian does not have direction restrictions as a vehicle on a road. Moreover, the pedestrian has a greater degree of freedom of motion in the layout and may chose from a plethora of self-determined paths in any given open area.

The images of the layouts may include images of a real-world building floor plan, a parking lot, a park, an indoor or outdoor recreation area, and/or other interior and exterior area plans corresponding to places where a person can walk or move (e.g., via a wheel chair, a bicycle, or other mobile assistance device). The images are pre-existing or publicly available images. For example, the images are originally formed or created for purposes other than generating a routable map. The pre-existing images may be generated by an entity separate from a developer of a routable open area map and/or its end user. The pre-existing images are available to the public or an entity for free or for a purchase price (e.g., online). Alternatively, self-generated images, images originally generated for creating a routable map, or non-public images may be used.

The image source 104 is in communication with the device 112 via the network 108. The network is the Internet, an intranet, a local area network (“LAN”), a wide area network (“WAN”), a virtual private network (“VPN”), a local wireless or wired connection (e.g., a USB connection or other device connection), and/or any known or future network or connection.

The device 112 receives images of layouts from the image source 104 for generating routable open area maps. The device 112 is a workstation, computer, editing device, beacon or map beacon, and/or other computing or transmitting device. For example, the device 112 is an editing workstation. The device 112 includes, but is not limited to, a display 124, a processor 128, a memory 132, an application 134, and an input device 136. Additional, fewer, or different components may be provided. Audio components may be provided. For example, a speaker, audio jacks, and/or other components for outputting or receiving audible or sound signals are provided.

The display 124 is any mechanical and/or electronic display positioned for accessible viewing in, on, or in communication with the device 112. For example, the display 124 is a touch screen, liquid crystal display (“LCD”), cathode ray tube (“CRT”) display, or a plasma display. The display 124 is operable to display images, such as images of layouts, floor plans, maps, or other areas. The input device 136 is a button, keypad, keyboard, mouse, trackball, rocker switch, touch pad, voice recognition circuit, or other device or component for controlling or inputting data in the device 112. The input device 136 may be used to perform functions, such as modifying received images (e.g., adding doors or openings) or using eraser tools.

The processor 128 is in communication with the memory 132, the application 134, the display 124, and the input device 136. The processor 128 may be in communication with more or fewer components. The processor 128 is a general processor, application-specific integrated circuit (“ASIC”), digital signal processor, field programmable gate array (“FPGA”), digital circuit, analog circuit, or combinations thereof. The processor 128 is one or more processors operable to control and/or communicate with the various electronics and logic of the device 112. The processor 128, the memory 132, and other circuitry may be part of an integrated circuit.

The memory 132 is any known or future storage device. The memory 132 is a non-volatile and/or volatile memory, such as a Random Access Memory “RAM” (electronic), a Read-Only Memory “ROM” (electronic), or an Erasable Programmable Read-Only Memory (EPROM or Flash memory). A memory network may be provided. The memory 132 may be part of the processor 128. The memory 132 is operable or configured to store images of layouts received by the image source 104. The memory 132 may also store images or data generated by the processor 128.

The processor 128 is operable or configured to execute the application 134. The application 134 is a software program used to generate open area maps that are routable based on pre-existing images, such as the images received from the image source 104. For example, the processor 128 runs the application 134 and creates or generates or assists in generation of a routable map via input from the input device 136 and/or automated commands. The application 134 may be stored in the memory 132 and/or other memory.

The device 112 is operable or configured to send or transmit one or more generated routable open area maps to the user device 116, or the user device 116 may request a routable open area map via the network or connection 120. The connection 120 is the Internet, an intranet, a local area network (“LAN”), a wide area network (“WAN”), a virtual private network (“VPN”), a local wireless or wired connection (e.g., a USB connection or other device connection), and/or any known or future network or connection.

Alternatively, the device 112 may store, upload, or send one or more generated routable open area maps or data thereof to the database 170. The database 170 may be a database, a memory, a website, a server, a beacon, or other device used for storing, receiving, and/or transmitting data corresponding to the routable open area maps. For example, the database 170 may store data entities that represent different layers of the open area map, such as data corresponding to reference regions, cost, restrictions, a grid or array, image data, and/or other content. The user device 116 may obtain a routable open area map or data thereof from the database 170 via the network 180, such as without communicating with the device 112. The network 180 is the Internet, an intranet, a local area network (“LAN”), a wide area network (“WAN”), a virtual private network (“VPN”), a local wireless or wired connection (e.g., a USB connection or other device connection), and/or any known or future network or connection.

Also, routable open area maps may be “pushed” onto the user device 116. For example, beacons, map beacons, or other devices can transmit or send routable open area maps or related content to the user device 116 based on the location or position of the user device 116. In one embodiment, a beacon can be placed at an entrance or passageway of a building or other area, and once the user device 116 comes within a certain range of the beacon, a routable open area map associated with the area and/or other related areas is sent to the user device 116.

The user device 116 is used to operate one or more routable maps to allow a user to navigate in or on respective layouts or areas. The user device 116 is a cellular telephone, a mobile phone, a personal digital assistant (“PDA”), a watch, a personal navigation device (“PND”), a computer, a digital floor plan device, a portable or non-portable navigation device, a kiosk, and/or other fixed, removable, or transportable digital device. The user device 116 includes, but is not limited to, a display 140, a processor 144, and a memory 148. Additional, fewer, or different components may be provided. For example, audio and/or application components may be provided. The display 140, the processor 144, and the memory 148 may be similar to or different than the display 124, the processor 128, and the memory 132, respectively.

In one embodiment, a user, such as a person working on a building floor, may want to be able to route or navigate about his or her building floor. Accordingly, an image of the layout or floor plan of the user's floor, which is stored in the image source 104, is transmitted and received at the device 112. Another entity, such as a map developer, operates the device 112. The map developer may be a person, company, or entity that develops maps for navigation or obtains and maintains map data and/or a geographic database, such as NAVTEQ North America, LLC located in Chicago, Ill. The map developer views the pre-existing image of the layout on the display 124 and generates a routable map based on the pre-existing image via the input device 136 and the software application 134. Automated commands and/or processes may be used in development of the routable open area map. Alternatively, the creation or generation of the routable open area map may be substantially entirely automated. The user may download or receive the routable map of his or her floor on the user device 116. For example, the user uses the user device 116 to download the routable map or data thereof from the device 112 or a storage site or component associated with the device 112 (e.g., via the connection 120, such as a USB connection, a wireless connection, or other connection). Alternatively, the user may download the routable map on a device (e.g., a computer or a jump/thumb drive) different than the user device 116 and then transfer the data associated with the routable map to the user device 116 or other user device. The user then uses the device 116 to display the routable map for routing, guidance, and/or navigation purposes regarding the building floor.

FIG. 2 is one embodiment of an image 201 of a layout used in the system 100. The image 201 is a pre-existing or publicly available image (e.g., is associated with the image source 104 or other source) that can be downloaded from the Internet or other network. For example, the image 201 may be downloaded, received, obtained from a website or other source. The image 201 represents a real-world layout or floor plan of a building floor, such as a first floor or other floor. The image 201 includes graphical representations or icons of areas, spaces, and/or designations in the layout. For example, the image 201 includes image reference objects, such as a men's room 217, a women's room 221, a cafeteria 225, offices 229, a conference room 233, a lab 237, a desk 241, and elevators or elevator bank 245. Image representations of doors 249 are also provided. The doors 249 are shown as a gap or opening in respective image reference objects. Alternatively, a door may be represented using a door symbol or image object 253 rather than an opening. Or, there may not be a representation of a door or opening.

The image 201 also includes an image representation of an open space, a walking grounds, a common or public area, and/or a hall area 209 for people to walk or move about to get from one place to another on the floor. Walls or barriers are depicted by corresponding, associated, or contiguous pixels or lines (e.g., a heavy line) of substantially the same or similar color. Entrances and/or exits 213 are depicted as openings or gaps in the walls or barriers that allow access between the interior area 209 and an exterior area 205. The exterior area 205 may represent an outer hallway, an outside of the building (e.g., a sidewalk, street, or road), or other exterior environment.

FIG. 3 is one embodiment of the image 201 corresponding to or undergoing a process used in the system 100 of FIG. 1. For example, the image 201 is downloaded or received at the device 112. The image 201 is used to create or generate an open area map that is routable. For example, a grid, mesh, or array 300 is applied on or over the image 201 or a copy of the image 201. The grid, mesh, or array 300 may be a grid or array of geometric shapes (e.g., uniform sized geometric shapes), such as tiles, sections, blocks, points, dots, circles, polygons, or other shapes. The grid or mesh 300 covers an entire ground area of the image 201. A ground area refers to a surface, plane, or floor or a portion thereof that can be walked upon as well as the surface in which objects or barriers may be placed or positioned on or over.

The grid or mesh 300 includes areas, sections, blocks, or tiles 304. Alternatively, the grid, mesh, or array 300 may include unconnected dots or points corresponding to areas or sections similar to the tiles 304 (e.g., the dots or points replace or act as a substitute for the tiles 304). The tiles 304 have a substantially rectangular or square shape and are substantially uniform in size. Alternatively, the tiles 304 may have a circular, triangular, or other geometric or polygon shape, and the tiles 304 may be different sizes at different locations rather than being uniform.

The grid 300 may be applied over certain areas of the layout rather than the entire image or entire ground area. For example, the grid 300 may be applied only in hallway areas, such as the interior area 209. In such as case, the grid 300 has a shape that corresponds to a pedestrian-accessible contiguous sub-area within the real-world area in which the shape has a boundary that corresponds to the walls in the pre-existing image. The grid 300 or portions thereof may also be applied to areas designated within an image reference object (e.g., the inner area of a room). Also, tiles may automatically fill into contiguous open areas. For example, a hallway or corridor area may be selected to automatically fill the area with tiles or sections of a grid or mesh.

The tiles 304 may be assigned or designated coordinates, such as local or global map coordinates. For example, each center of a tile 304 or other part of the tile is given a (x,y), latitude and longitude, or other coordinate designation. One of the tiles 304, such as at a corner of the image, may be designated as an origin point (0,0) for reference and positioning purposes. The coordinates allows items, features, or regions to be searchable. However, for routing purposes, the coordinates may not be used.

FIG. 4 is one embodiment of the image 201 corresponding to or undergoing another step or process after the mesh 300 has been overlaid. Tiles that are not to be walked on or that are non-navigable are provided as tiles or area 401 (e.g., the tiles or area 401 may be replaced with unconnected dots or points that represent non-navigable areas). For example, tiles surrounding or under or associated with borders or walls of the image reference objects (e.g., reference objects 217, 221, 225, 229, 233, 237, 241, and 245) are selected to be or are designated as non-navigable tiles 401. Also, the image representation of the border, barrier or wall between the interior hall area 209 and the exterior area 205 is associated with the non-navigable tiles 401 for routing purposes. The tiles 401 allow routes to be prohibited from passing through walls or barriers to represent a real-world experience. However, doors 249 and 253 are associated with navigable tiles 304 to allow routing in and out of rooms or areas surrounded by tiles 401. Alternatively, if no doors or openings are present or created, tiles substantially adjacent or proximate to reference areas may be used for routing to and from respective reference areas.

The non-navigable tiles 401 may be or represent tiles (or dots or points) removed from the grid 300 or may be tiles (or dots or points) designated with a non-navigable status. The non-navigable tiles 401 or the lack thereof may be represented as blank spaces, in which spaces that are free of the grid or tiles are not navigable for routing purposes. Alternatively, the non-navigable tiles 401 may be colored differently than the navigable tiles 304.

Navigable or non-navigable tiles, dots, or points may be sub-classified. For example, each or some tiles may be associated with a feature or location related to the layout. In one embodiment, tiles may be linked or correspond to a washroom area, a narrow area, a windowed area, a dimly lit area, a high traffic area, a low traffic area, or other area or feature. By classifying or sub-classifying the tiles, one can input preferences for routing purposes. For example, a user may want to avoid high traffic areas, and, accordingly, the user may input his or her preference before or during routing.

A wrap or boundary feature may be used regarding the grid 300. In certain cases, a person may want to route from one point in the interior area 209 to another point in the interior area 209, but a path is generated that routes the person out into the exterior area 205 and back into the area 209. Such routes may occur when it is optimum to route outside and back inside (e.g., when having multiple openings between interior and exterior areas). However, to avoid any routing to tiles in the exterior area 205, a wrap or boundary feature may be used that bounds all routing within the area 209 and associated areas. For example, a boundary line or designation may be allocated along the circumference of the inner area. However, the boundary feature will allow routing to the exterior area 205 when a user selects a destination point to be in the exterior area 205 or outside an inner area. Alternatively, the tiles of the exterior area 205 may be designated as non-navigable, or openings to the exterior area 205 may be associated with non-navigable tiles 401.

A connection point 405 is also provided. The connection point 405 may be generated or provided in a spatial or data layer separate from the grid or mesh 300. The connection point 405 is represented as a tile 304 or a subset of tiles 304 within an area. The connection point 405 may encompass the entire area of the elevators 245 or a portion thereof. Alternatively, the connection point 405 may not be associated with a reference image object or reference region. The connection point 405 represents or acts as a link to another map, such an open area map that is routable, for routing and navigation purposes. For example, the connection point 405 may correspond to one or more elevators, a stairwell, an escalator, a ladder, or other feature for moving a person to another floor or area. A plurality of connection points 405 may correspond to respective individual elevators or features. In one embodiment, the connection point 405 is used to route between an area or point from the image 201 to another point or area on another map or floor plan, such as another map or floor plan representing another floor of the building (e.g., a second floor, a third floor, or Nth floor). Alternatively, the connection point 405 may represent a connection for moving or transferring a person from one point to another point on the same floor or ground area. For example, the connection point 405 may correspond to a moving walkway or other transportation device. Also, the connection point 405 may represent a connection to another routable open area map associated with the same level or area. For example, in one open area map, a route may be generated to an area that is represented by a blank, unspecific, or general polygon or shape that represents a reference area, such as a food court. A connection point can be placed at, by, or on the general polygon that represents the reference area in which the connection point corresponds to or directs one to another routable open area map that has detailed features and/or reference regions within the original reference area (e.g., the food court). The general or parent open area map (the food court reference area) may be displayed, and then when one routes to or selects the specific or child open area map (the reference regions or areas within the food court), the child open area map may be displayed, such as in a separate window or different screen.

FIG. 5 is a diagram showing reference regions 500 corresponding to the image 201. In a spatial layer separate from the grid 300, the reference regions 500 are generated. For example, the image reference objects 217, 221, 225, 229, 233, 237, 241, and 245 in the image 201 are part of a raster image or a pixilated image. The raster image may be binarized (e.g., converting pixels to black and white pixels and/or 1's and 0's). The device 112 extracts names or descriptions associated with the image reference objects. The separation allows for facilitation of optical character recognition (“OCR”) to generate text 504 corresponding to the names or descriptions associated with the raster image 201. The text 504 is used for searching or associating different areas of an open area map. The text 504 may match the names or descriptions of the image 201. Alternatively, additional or different text or information may be added. For example, text “A,” “B,” “C,” “D,” “E,” “F,” and “G” are added to the “office” text for differentiation purposes. The added text may or may not be visible to an end user.

After graphics-text separation, the image reference objects go through vectorization to form the polygons, reference regions, or areas 500. The reference regions 500 correspond to the different areas, rooms, or spaces in the image 201. The reference regions 500 are associated with or correspond to respective navigable tiles 304 and respective non-navigable tiles 401 represented by the grid 300 on a different spatial layer.

The grid or mesh layer may be compiled with the reference region layer, a connection layer, and/or other spatial or data layers, such as a cost layer or restriction layer, to form or generate an open area map that can be used for navigation and/or routing.

FIG. 6 shows one embodiment of an open area map 601 generated by the system 100 of FIG. 1. The open area map 601 may be displayed on the display 140 of the user device 116 or other display. The open area map 601 includes graphical representations of the reference image objects of the image 201. For example, the image 201 is used as a background or base image for the open area map 601. Alternatively, different graphics or images are generated (e.g., based on the generation of the reference regions 500) to represent the original layout of the image 201. The grid 300, including the navigable tiles 304 and the non-navigable tiles 401 or lack thereof, compiled with the reference regions 500 and the connection point 405 underlie the open area map 601 for routing and navigation purposes. For example, the grid 300 or compiled grid may not be seen by a user. Alternatively, the grid 300 and/or other features may be exposed to the user.

FIG. 7 shows one embodiment of an open area map 700 generated by the system 100 of FIG. 1. The open area map 700 represents another floor of the building that includes the floor represented by the open area map 601. The open area map 700 includes image reference objects, such as a breakroom, a conference room, elevators or elevator bank, offices, and a gym, as well as associated reference regions, a grid, a connection point 708, and navigable and non-navigable tiles similar to the respective features of the open area map 601 discussed above.

In one embodiment, a user may want to use the open area maps 601 and 700 to route from an office on one floor to the gym on another floor of the building. Referring to FIG. 6, the user searches for the office, using a text search, to designate an origin point 609. The text for the particular office is associated with the respective reference region 500, which is associated with respective tiles 304 and 401. Alternatively, the user physically touches or selects the origin point 609 on the display. Or, the origin point is determined based on a global positioning satellite (“GPS”) system or device, an indoor location system (e.g., WiFi based), or the fact that the location of the origin point is fixed (e.g., a kiosk or a floor plan device on a wall). The origin point 609 may correspond to one or more tiles within or associated with the reference region or reference image object of the office or may correspond to the entire area. Referring to FIG. 7, the user then searches for the gym, using a text search, to designate a destination point 712. The text for the gym is associated with the respective reference region for the gym, which is associated with respective tiles. Alternatively, the user physically touches or selects the destination point 712 on the display. The user may switch to the open area map 700 or may view both open area maps 601 and 700 on the same screen or window.

After the origin point 609 and destination point 712 are selected, various routes are calculated and/or compared based on the underlying compiled grid. The routes may be calculated based on a Dijkstra method, an A-star algorithm or search, and/or other route exploration or calculation algorithms. Various aspects, such as distance, non-navigable areas, costs, and/or restrictions, are considered to determine an optimum route. A path 605 (FIG. 6) is generated based on the calculation. The path 605 is displayed for the user to view and follow. The path 605 shows a path that starts from the origin point 609 in the office, passes the conference room, and uses the elevators via a connection point 613, such as the connection 405. Then the open area map 700 shows a path 704 (FIG. 7) that starts from elevators at a connection point 708 and leads to the gym at the destination point 712.

The calculation and determination of the routes and/or the paths 605 and 704 are based on or formed of adjacent, continuous, or connected tiles. For example, navigable tiles that border or touch each other are considered for point-to-point routing, in which any area in the layout or any point associated with adjacent tiles can be routed to based on calculation regarding the grid or mesh (i.e., not solely pre-determined routes). Adjacent tiles forming a route may be connected or linked by their center points or other parts.

FIG. 8 is a flowchart of a method for generating an open area map, such as the open area map 601 or 700. Fewer or more steps or acts may be provided, and a combination of steps may be provided. Also, the steps or acts may be performed in the order as shown or in a different order. The method is implemented by the system and/or devices described herein or by different devices or systems.

In one embodiment, a graphical representation or an image of a layout, such as the image 201, is obtained or received (Step 801). For example, a map developer using a workstation, computer, or other device, such as the device 112, downloads or requests a pre-existing image of a layout, such as a building floor plan, via the Internet or other network or connection, such as the network 108. The graphical representation of the image may be stored or located at a website, server, file, another computer or other device, or any other storage device or area, such as the image source 104. The image of the layout may be received wirelessly and/or through a wired connection. The received image may be modified. For example, eraser or drawing tools or functions may be provided so that the map developer can add or remove image features. In some cases, doors or openings may need to be added for routing purposes.

A grid, mesh, or array, such as the grid or array 300, is applied or overlaid on or over the image of the layout, a copy of the image of the layout, or a modified image of the layout (Step 805). The map developer assigns a scale by designating a distance measurement within the layout. For example, using a mouse or other input device, such as the input device 136, the map developer selects a space or distance between image objects, such as the image objects 217, 221, 225, 229, 233, 237, 241, and 245, representing a width or length of a hallway or area. The map developer then assigns a value to that space or distance, such as 1 meter or 3 meters. Alternatively, designating a distance measurement may be entered via a “pop-up” screen or a fill-in box, or the distance measurement may be automatically implemented based on pre-existing distance markers in the image or pre-determined parameters. By assigning a scale, an understanding of distances between objects and areas within the layout is achieved.

The grid or mesh is then applied on the image of the layout, or the grid or mesh is applied before assigning the scale. For example, a grid covering substantially the entire image of the layout is provided. Alternatively, certain or specific portions are chosen for applying the gird. In one embodiment, the grid may be applied to only areas designated for walking between reference objects, such as hallways or other ground or open areas. Therefore, the grid or mesh does not intersect borders, barriers, and/or walls within the image. Also, the grid or mesh may be applied on internal areas, such as areas within a room or image reference object. The map developer may choose where to apply the grid, portions of the grid, or multiple grids that may be joined via the input device. For example, the map developer may click on or select a hallway area within the layout to apply a grid throughout the hallway area. In alternate embodiments, a grid or a portion thereof is automatically overlaid over substantially the entire image of the layout or portions of the layout based on color/image recognition or other parameters.

The grid, mesh, or array is composed of tiles, blocks, sections or areas, such as the tiles 304, or similar or corresponding dots or points, as mentioned above. Based on the scaling, the tiles are assigned or correspond to a measurement value. For example, each tile may have a measurement value of about 1 square meter, ¼ square meter, or other value. Alternatively, each tile may have any other measurement value or different values from each other. The resolution or number of tiles or points may be adjusted by the map developer or automatically. For example, for a finer resolution, the grid or mesh may be adjusted or changed to include more tiles or points, and for a lower resolution, the grid or mesh may be adjusted to include fewer tiles or points. The adjustment of the number of tiles or points may be based on the number or positioning of image reference objects within the layout and/or other factors. For example, the size of the tiles may be selected to match a human or pedestrian scale so that at least one navigable tile may fit in narrow or narrowest passages in the real world environment. A maximum tile size (e.g., at most about 15, 20, or 30 inches in length and/or width or other length, width, dimensional, and/or area value) may be chosen or be pre-determined to allow for navigable tiles to be placed in the narrowest or smallest areas, hall, or corridors for routing. An appropriate tile or area size is chosen to avoid the lack or inability of routing in some suitable areas of the layout. Also, non-uniform sized tiles and/or shapes may be used for different areas. For example, larger areas may use larger sized tiles and smaller or narrow areas may use finer or smaller sized tiles.

Local or global map coordinates are assigned or designated. For example, center of the tiles or other parts of the tiles (or points or dots of an array or grid) are given a (x,y), latitude and longitude, or other coordinate designation. An origin is selected by assigning a (0,0) or origin point to one of the tiles (e.g., a corner tile). The coordinates can be used for searching or identifying reference image objects, reference regions, or other features or vice versa. Point-to-point routing may, however, be based on adjacent or contiguous tiles, and, therefore, the coordinates may not be needed for routing calculations. Alternatively, the coordinates may be used for distance and cost determinations when calculating a route.

A routable map, such as the map 601 or 700, is generated or created based on or as a function of the grid or mesh (Step 809). FIG. 9 is a flowchart showing an example of a method for generating the routable map including steps that may be wholly or partially encompassed by Step 809. A non-navigable area is designated in the grid or mesh (Step 900). For example, the map developer clicks on or selects areas within the layout of the image to convert them to non-navigable tiles or areas, such as the non-navigable tiles or areas 401. The map developer may select images of walls or barriers that cannot be walked through in the real world as non-navigable areas. The selection may assign tiles with a non-navigable status or may remove tiles. The designation of non-navigable areas may also be automated. For example, instead of selecting multiple areas in the image to be non-navigable, the map developer may click on or select a wall or barrier to be non-navigable and all other features or image objects with the same or similar color or pixel level of the selected wall or barrier may automatically be associated with non-navigable areas or tiles. Alternatively, pre-determined color or pixel levels or image recognition factors may be entered so that non-navigable tiles or areas are automatically generated once a grid is overlaid without involvement of a map developer or other entity. In such automated cases, graphical representations of text or descriptions of image objects in the layout may be removed or separated prior to designation of non-navigable areas. This is so because the descriptions may be mistakenly assigned as non-navigable areas. Alternatively, a non-navigable area may be designated by originally not applying a grid or a portion thereof to areas intended to be non-navigable.

A plurality of reference regions or areas are generated (Step 904). The generation of the reference regions occurs on a different spatial layer than the grid or mesh. The grid or mesh may or may not be viewed when creating the plurality of reference regions. In one embodiment, the plurality of reference regions are automatically or semi-automatically generated. For example, a plurality of reference image objects are identified or determined in the image, such as the image 201, which may be a raster image or a vector graphics image. A raster image of the layout is binarized. Binarization of the image allows for logically comprehending the layout by using digital 1's and 0's. For example, a Trier-Taxt binarization is used. The Trier-Taxt binarization provides for edge preservation. Alternatively, other binarization techniques or methods may be used. The binarization may depend on three parameters or factors, such as a sigma, an activity threshold, and a pruning factor. Alternatively, more or less factors may be considered.

The sigma is a larger sigma rather than a lower sigma that may correspond to noise sensitivity. Activity at a pixel may be proportional to a local average of a gradient magnitude, and pixels with lower activity than the activity threshold may be set to zero. The pruning factor is used for removing small connected components. In one embodiment, the sigma is set to about 1, the activity threshold is set to about 2, and the pruning factor is set to about 1. Alternatively, the factor values may be set to any other value and may be adjustable.

Regarding identification of the reference image objects, a text/graphics separation is performed after binarization. For example, the graphical description or text corresponding to each of the reference image objects is separated from the respective image objects. Any future or past graphics-text separation may be used. The separated text is linked to or identified with the respective image object. For example, a text region may be designated in each of the reference image objects. After the separation, OCR is performed on all or some of the graphical descriptions to convert them into searchable text, such as the text 504, or text that can be recognized as having meaning or a definition rather than a graphical representation of text. Separation of the graphical descriptions may facilitate or improve the OCR. Alternatively, the OCR may be performed without the separation. Text aliasing may be reduced by doubling or increasing resolution of the original image of the layout, such as by using Lanczos re-sampling before applying OCR. In alternate embodiments, other text recognition methods, functions, or algorithms may be used.

The plurality of reference regions, such as the reference regions 500, are generated by forming borders or boundaries corresponding to the respective reference image objects. For example, after binarization and/or graphical description separation, the reference image objects are vectorized. Lines or vectors are generated or created between the digital or binarized data points to form shapes corresponding to the image objects within the layout. For example, the Rosin and West vectorization algorithm is used. Alternatively, other future or past vectorization algorithms may be utilized.

Closed polygons are identified to determine the reference regions associated with the original reference image objects. For example, based on the vectorization, closed polygons or other shapes are determined. The closed polygons may be determined via planar curve, vertices, edge, and/or face techniques. Any future or past computational-geometry algorithms or methods may be used. A closed polygon may correspond to an office, a room, or other area.

Some reference image objects may include gaps or symbols of doors, such as the gaps or symbols 249 and 253. For the purpose of determining reference regions, all line segments identified in the vectorization may be visited to determine or identify gaps that can be closed to form a closed polygon. The gaps are closed to identify the respective reference regions. Regarding symbols of doors, the map developer may identify or provide information that links a unique symbol, such as the symbol 253, to a door, opening, entrance, and/or exit. The association may be stored in a memory or look-up-table. After or during vectorization, the symbols of the doors can be identified based on matching and replaced with gaps. The gaps are then closed to identify the respective reference regions. Alternatively, a line or vector replaces the symbol of the door to close the polygon rather than forming a gap and then closing the gap. Multiple gaps or symbols of doors for a given image object may be visited or closed to form a closed polygon for determining a reference region. The gaps or symbols of doors correspond to navigable tiles on the grid that is in a separate spatial layer relative to the reference image objects. The doors or openings may be inferred by comparing the navigable tiles of the grid with respective reference regions.

The names or text associated with each of reference image objects are populated in a name attribute corresponding to the generated reference regions. For example, the text generated from the OCR is associated with text regions of the generated reference regions. A look-up-table, database, or other memory feature links the text descriptions to each respective reference region. A question and answer feature or a verification function may be implemented so that the map developer can correct errors in the generated text or association of text with reference regions. A reference region may be searchable based on the associated text and vice versa.

The reference regions may also be associated with a reference type. For example, each reference region may correspond to or be designated a type, such as a restaurant, office, department store, grocery store, bathroom, or other designation, based on the associated text, function, purpose, and/or other factors of the reference region. These types or keywords may be stored in a database or look-up-table and may be linked or associated with respective reference regions. The type or tag may be more specific, such as particular names of stores or areas (e.g., McDonalds™ restaurants) that may or may not be different than the generated text or name. Also, logos and/or respective websites may be associated with the reference regions. A reference region may be associated with one or more types or tags and may be searchable based on the types or tags.

The reference regions and associated text and type may be generated manually instead of or in addition to being automatically generated. For example, the map developer, using program or application tools, may outline or replicate the reference image objects in the original image of the layout to generate the reference regions, such as the reference regions 500, in a spatial layer separate from the grid or mesh. Also, the map developer may read or view the original descriptions of the reference image objects and enter, input, or type in equivalent text, such as the text 504, and/or types to be associated with the generated reference regions.

The generated data or data layers associated with a digital open area map, such as the grid or array and the reference regions are stored, such as in the database 170. Separate data or spatial layers may be stored as individual XML files or other data. For example, data corresponding to the underlying image, the grid, and the reference regions are saved or stored. Position or location information or data corresponding to the grid or respective tiles (such as regular-sized tiles) as well as the reference regions are also saved and/or provided in the data structure. The position information is used as a spatial reference regarding appropriate location of the different data entities. The position information may be based on an original scale, a reference, or coordinates, such as relative to the underlying image. The database 170 may compile the separate data layers to form a routable open area map. Accordingly, the database 170 may stream or send the compiled open area map data to the end user device. Alternatively, separate data layers may be sent to the end user device for compilation on the end user device. Also, a compiled open area map file or data may be stored in the database 170 rather than storing separate data layers.

Different spatial or data layers are compiled or combined to form an open area map, such as the open area map 601 or 700, that is routable (Step 908). For example, the plurality of reference regions including the associated text and tags are compiled with the grid or mesh. The compilation links or associates respective tiles to the generated reference regions (such as tiles that are to be within a reference region, substantially adjacent to the reference region, and/or touching or intersecting a border of the reference region) for search, navigation, routing, and other purposes. Also, connections or connections points, which may be generated on a separate spatial layer, may be compiled with the grid and the plurality of reference regions. Other components or features, such as restrictions or cost features, that may be on separate or different spatial layers may also be compiled with the grid or mesh. Any future or past compilation technique or method may be used. Also, different spatial layers may be combined during a runtime. Alternatively, the grid, reference regions, and/or connection points, as well as other features, may be generated and exist on the same spatial or data layer rather than different layers. Accordingly, a final compilation may not be required. Also, some spatial layers may not be compiled or may not be used. For example, routing may be accomplished using navigable and non-navigable tiles without associating the tiles with generated reference regions.

Referring back to FIG. 8, another or second graphical representation or image of a layout, such as an image similar to the image 201, is obtained (Step 813). For example, the second image may be an image of a floor plan of another floor of the building (e.g., the image obtained at Step 801 represents one floor of a building and the image obtained at Step 813 represents another floor of the building). The second image may be obtained or received by the map developer in a similar manner as the first image was obtained at Step 801.

Another grid, mesh, or array is applied to the second image (Step 817), such as applying the grid at Step 805. Another or second routable map is generated based on or as a function of the second grid (Step 821), such as generating the first routable map at Step 809. The first and second routable maps are linked or associated with each other, such as via one or more connections or other features (Step 825). For example, a connection point in the first routable map is associated with a connection point on the second routable map for routing purposes. The connection points may correspond to an elevator connection, such as the connection points 613 and 708, or other connection linking two floors of a building or other areas. Alternatively, one or the same connection point is used to link the two routable maps. Any number of routable maps may be linked together via one or more connection points or other features (e.g., 1 to an Nth number of routable maps corresponding to different floors of a building or other areas may be generated and linked or associated together).

FIG. 10 is a flowchart of a method of routing in an open area map, such as the open area map 601 or 700. Fewer or more steps or acts may be provided, and a combination of steps may be provided. Also, the steps or acts may be performed in the order as shown or in a different order. The method is implemented by the system and/or devices described herein or by different devices or systems.

In one embodiment, an end user, such as a pedestrian, uses a device, such as the device 116, for point-to-point routing or navigation in an open area. For example, one or more routable open area maps or data thereof, such as the open area map 601 or 700, are downloaded or sent to the user device, such as via the connection 120 or other connection. Alternatively, one or more routable open area maps or data thereof are “pushed” onto the user device via a proximity beacon or transmitter or other device based on location or position.

The user views one or more open area maps, such as via the display 140. An origin or origin point, such as the origin point 609, is selected (Step 1001). For example, the user types in or enters an area or point of origin that acts as a starting location for routing. The user may enter a name or text describing a reference region, and the respective area in the open area map may be allocated as the origin point based on searching or accessing a look-up-table linking reference regions with names or text. Alternatively, the user may click on, select, or physically touch an area on the open area map (i.e., touch the display screen) to choose the origin point.

The origin selected in the open area map is identified (Step 1005). For example, one or more tiles associated with the origin point or reference region associated with the origin point is determined, considered, recognized, targeted, focused upon, and/or highlighted for route calculation.

A destination or destination point (i.e., the place or area the user wants to be routed to), such as the destination point 712, is selected (Step 1009) by the user in a similar manner to selecting the origin point or through different methods. The destination selected in the open area map is identified (Step 1013) in a similar manner to identifying the origin point or through different methods.

A route from the selected origin to the selected destination in the open area map is calculated (Step 1017). For example, adjacent or connected tiles that are navigable, such as the tiles 304, are assessed to determine an optimum or preferred route from the origin point to the destination point. Non-navigable areas or tiles, such as the tiles 401, are avoided or routed around. One or more possible routes may be calculated using geometric and/or mathematical functions or algorithms. For example, centers or other locations of each of the tiles are connected or associated with each other to form potential routes. An optimum route is chosen based on distance as well as other factors, such as cost, restrictions, or user preferences that may be inputted (e.g, a user may want a route to avoid or pass by a desired area). The user preferences may be based on classification or sub-classification of tiles. For example, each or some tiles are associated with a feature related to position, location, and/or type of area (e.g., major, intermediate, or minor corridor, hallway, pathway, or area, high or low traffic area, unpopular or popular area, scenic area, narrow area, isolated area, sloped area, flat area, carpeted area, or size, length, or width of an area). The tiles may also be sub-classified based on what reference regions or areas they are linked to, proximate to, or pass by. Different tiles may be ranked or ordered based on the sub-classification. In one embodiment, the user may input or choose to avoid high traffic areas or major corridors when routing.

A Dijkstra method, an A-star algorithm or search, and/or other route exploration or calculation algorithms may be used to form lines, curves, or routes between the points of the connected tiles. A Douglas-Peucker method or algorithm may be used to smooth or simplify the calculated lines or routes. For example, by connecting the center of adjacent tiles together, jagged, sharp, or triangular edges may be formed in the route from the origin point to the destination point. To minimize distance and provide a smooth line or curve for the route, the Douglas-Peucker algorithm can find or provide an averaged route from the origin to the destination. The Douglas-Peucker algorithm is modified to avoid non-navigable tiles and may be adjusted to change threshold levels for line smoothing or averaging. Alternatively, other line smoothing algorithms or methods may be used.

Calculated routes and generated paths may be saved or stored for future use. For example, once a path is generated, it may be saved as a pre-determined path that can be reused when a user desires to be routed from the same origin to the same destination. Some, rather than all, paths or routes may be saved. For example, routes or paths between major or popular reference regions may be stored while paths regarding less traveled or minor reference regions may not be stored. Also, partial routes or paths may be stored in which some parts of the path, not the entire path, are saved. Additionally, routes or paths between connections or connection points may be pre-calculated or predetermined and stored for routing. For example, a user may want to route from one point to another in which one or more connections may be used. In this case, a route is calculated from an origin to a connection as well as from the other connection to the destination, and the route between the connections has already been calculated, which saves time and processing. Routes may be stored, saved, ranked, or ordered in multiple data layers. For example, higher layers may include main, major, or more important routes. Alternatively, routes and paths are always recalculated and regenerated.

A path from the selected origin to the selected destination is generated based on the calculation of the route (Step 1021). After or during calculation and selection of one or more routes, all of the tiles associated with an optimum or preferred route are identified or determined as the path. For example, the Douglas-Peucker algorithm or other algorithm may form a line and/or curve that passes over certain navigable tiles. Those tiles are then identified, entered, stored, or highlighted as the path for the user to take to go from the origin point to the destination point. The determined path then is displayed, such as the displayed path 605 or 704, to the user in the open area map for routing purposes.

In one embodiment, the user may receive partitioned data when using the open area maps for routing and/or navigation. User devices, such as the device 116, may include resource constrained components in which processing speeds, memory, or other features may not be as high, fast, or large as other devices. Accordingly, instead of downloading or executing all the data associated with multiple open area maps at the same time, data may be received or executed on an as needed basis. For example, a user may download or initiate one open area map or a portion thereof when beginning navigation (e.g., a first floor or a part of the first floor including the origin is displayed or loaded for routing). Then when the user enters or is routed to a connection or connection point (e.g., to go to a second or other floor or area), the connected open area map data is then downloaded or initiated for continuing the routing process. Also, different spatial layers or features of an open area map may be downloaded or executed on a partitioned basis or at different times.

The open area maps discussed above may or may not include navigation related attributes or nodes and road or path segments that are collected and organized into a geographic database, such as used for in-vehicle navigation systems, portable navigation devices, real-world vehicle navigation maps, and/or real-world pedestrian navigation maps. The navigation attributes may include turn restriction content, speed limit information, optimal or popular path data, footpath content, sign information, and/or other attributes for performing navigation related functions, such as route calculation, destination time calculation, route guidance, and/or other real-world navigation functions.

The open area maps may be connected or in communication with real-world vehicle and/or pedestrian maps or map data that are based on or include collected and organized navigation attributes and/or nodes and links or road/path segments. For example, an open area map of a floor of a building, a building, or other open area map may connect to a road network map for routing and navigation purposes. A user may use a device to route within a building floor to navigate him or her to an outside area, such as the area 205 (FIG. 2). Once the user reaches the outside area, the user may want to use a set road network to navigate to another part of a city or other location. The user's device or other device that can communicate with the user's device may execute, bring up, or show a vehicle navigation map that performs navigation related functions regarding the road network. Any combination of open area maps and navigation maps or data based on collected attributes may be connected with each other for routing and/or navigation purposes.

Alternatives

In the description above, the open area maps used for routing focus on building floors or floor plans. However, the features described may be used for any number of open areas. For example, images of layouts of parks and outdoor environments may be obtained and used to generate routable maps, as described above. Different sections of a park, such as picnic areas, jungle gyms, slides, restrooms, and other areas, may be defined as separate reference regions. Therefore, routing can be generated over grassy areas similar to routing between offices mentioned above. Parks may have walking paths that may be incorporated in routing. Alternatively, pre-determined walking paths or routes may be avoided in routing. Also, non-navigable tiles may be used or implemented for borders or barriers. For example, lakes, ponds, or other water areas in the park may be bordered with non-navigable tiles so that one is not routed through water. Other barriers or desired boundaries, such as hazardous areas, train tracks, or rocks, may be associated with non-navigable tiles. Alternatively, navigable tiles may be used if there is a reason to pass through some of these boundaries. For example, if a boat exists to take a person from one side of a lake to another, then a boat area may be associated with navigable tiles.

The tiles or objects associated with the image of a park or outside area may be sub-classified. For example, some tiles may be associated with grass areas and some tiles may be associated with sidewalks. A user or other entity may input a preference, such as grass only, sidewalk only, or other designation, for routing purposes. Accordingly, routes may be generated by avoiding or using certain specified tile types (e.g., generating a route over only grass areas and avoiding sidewalks or vice versa).

In another embodiment, a pre-exiting image of a parking lot may be obtained and used to generate a routable open area map. Each of the individual parking spaces may correspond to different reference regions. The outlines of the parking spaces may be considered barriers that may or may not be associated with non-navigable tiles. For example, the outlines of the parking spaces may be designated as non-navigable areas so that a route is not generated through parking spaces (e.g., for safety to pedestrians, cyclists, or others, and also for practicality because the spaces may be filled with cars). However, certain areas of the outlines of the parking spaces may be designated as navigable to simulate the concept that pedestrians may walk or navigate between parked cars. The parking lot may have multiple levels of parking floors, which may be associated with each other via a connection, such as the connection 405, 613, or 708, representing an elevator, stairs, or other connection.

Other areas or environments may be used to generate routable open area maps. For example, pre-existing images of amusement parks, malls, museums, and other indoor or outdoor areas may by obtained and used for generating routable maps or plans. In one embodiment, an image of a trade show area or floor plan or other temporary layout may be obtained. For example, the layout setup for a trade show may last or exist for only about a week, less than about 3 months, or other time periods. The image of the temporary layout may be obtained and used to generate a routable open area map as described above. Therefore, after a certain time period (such as less than about 3 months or other temporary time period), the generated routable map may no longer be applicable for the location or area. Also, the generated open area map may be time boxed based on the time period of the temporary layout. For example, the open area map or portions thereof, such as reference regions or other features, may disappear, be erased, or be inoperable when the actual layout is changed or taken down after the allocated time period. The open area map or features thereof may be erased by the executing device based on a timer within the device or a communication or signal from an outside source. Also, events or features associated with certain reference regions may be time boxed or used to time box the specific reference regions. For example, a speech, show, or activity may occur at a specific area (e.g., reference region) for a certain time period. Accordingly, the reference region may be only routable or may only exist for the specific time period associated with the speech, show, or activity. In another alternate embodiment, reference regions may be mobile, such as a mobile truck or moveable store, which makes the reference regions temporary for a specific location. Or, reference regions may be routable for a temporary time period based on how long an item is on sale for a given reference region, store, or stall.

In the description above, the application of the grid or mesh focuses on, but is not limited to, a two-dimensional format. The grid or mesh may be a three-dimensional grid or mesh including points or coordinates in an x, y, and z direction (e.g., the coordinates may include longitude, latitude, and altitude information or local coordinates). For example, the image of the layout obtained may include three-dimensional features. For example, a floor plan may have floor ramps, steps or stairs, a bi-level area, or other features that are displayed or designated in three-dimensional space. Also, a hill or peaks and valleys in a park area may be displayed or provided in a three-dimensional space. Therefore, a three-dimensional grid or mesh may be applied on or over the image to generate a routable open area map as described above. The addition of the z direction may require additional calculation for determining a route and/or path. For example, height may be a factor in determining an optimum or preferred route. Instead of using square tiles, triangular sections or tiles may be used for the three-dimensional grid or mesh. Alternatively, other geometrical shapes may be utilized.

A three-dimensional grid or mesh may be used for routing a person from one point to another in addition to helping a person find an object. For example, images of layouts of a grocery store or retail store having vertical shelves of products and goods may be obtained. A three-dimensional grid may be applied in which the floor area is overlaid with two or three dimensional tiles, and the vertical shelving areas are overlaid with a grid or mesh as well. Different products or goods on the shelves may be designated as reference regions. Accordingly, an open area map may be generated that can route a shopper or user to one place in the store to another place where a product can be found on a proximate or nearby shelf. Then a route can be calculated on the grid over the shelf or vertical area pointing to the specific or selected product. The shopper or user may not walk on the shelf, but the route may be useful in showing the shopper or user where exactly the product is on the shelf. Or, a route can be calculated to end at a ground or floor tile that is nearest to the shelf.

In another embodiment, instead of and/or in addition to using a grid, mesh, or array, as described above, color may be used to designate navigable and non-navigable areas. For example, the color white may be associated with navigable areas and the color black may be associated with non-navigable areas. Any number and types of colors may be used. Accordingly, routes may be calculated based on the placement of respective navigable and non-navigable colors. For example, paths or routes may be generated within navigable colored areas and around non-navigable colored areas based on distance algorithms. Also, different shades of color or gradation of color may be used as factors or cost for calculating or generating routes.

Furthermore, as described above, a map developer obtains an image and uses a workstation, computer, and/or device, such as the device 112, to generate a routable open area map. The open area map is then received by an end user or at an end user device, such as the user device 116. However, an end user or other entity separate from a map developer may obtain an image of a layout (e.g., an end user may take a picture of a layout via a camera that may or may not be part of the device 112 or 116 or the end user may obtain the image via the image source 104) and generate a routable open area map automatically and/or manually. For example, an end user may obtain and/or purchase a software application for creating open area maps from a map developer or other entity. The device 112 (FIG. 1) may be operated by an end user, such as a personal computer. Alternatively, instead of using the device 112 to generate a routable open area map and sending the open area map to the user device 116 for use, the user device 116 may be used to generate and use a routable open area map, bypassing the device 112. Or, the device 112 and the device 116 may be combined into one device or system.

Converting Open Area Maps

In other embodiments, open area maps, as described above, may be used to generate or create traditional link-node maps or data thereof, such as node data records, path segment data records, point-of-interest (“POI”) data records, and any other data records or attributes associated with navigation functions and data structures. FIG. 11 illustrates an exemplary embodiment of a routable open area map 1100, such as the open area map 601 and/or 700. In one embodiment, one or more routes or paths are generated using the open area map 1100. For example, a starting point 1108 is selected (such as by the map developer as mentioned above or another entity) or identified and a destination point 1112 is selected (such as by the map developer or other entity) or determined to generate a route 1104. Other routes may be generated as well, such as at substantially the same time or at different times. For example, a route 1116 is generated between points 1120 and 1124. In one embodiment, routes to all destinations or destination points are generated using mesh-based routing algorithms or other routing techniques. For example, multiple or different starting points or origins are used to route to the plurality of destinations on the open area map 1100 (wherein a destination may be any routable area or point on the map). Alternatively, less than all destinations are routed to on the open area map 1100. For example, major destination points are focused on for generating routes.

FIG. 12 illustrates generated data records based on the generated routes 1104 and 1116. For example, the map developer, other entity, or program thereof, determines nodes or node data records along the generated routes. In one embodiment, nodes 1201 and 1205, respective points along the generated routes 1104 and 1116, are generated. The nodes 1201 represent intersections or intersection points between links or path segments 1209. The nodes 1205 represent origin and/or destination points. Other links or path segments may be connected to the nodes 1201 and 1205. The path segments or links 1209 are different portions of the generated routes 1104 and 1116. The nodes 1201 and 1205 correspond to end points of the path segments or links 1209. The path segments and/or nodes may represent one or more dedicated routes or portions thereof in one or more specific areas that may be stored and retrieved for future routing or navigation-related functions.

FIG. 13 illustrates data record components and an exemplary geographic database 1320. For example, one or more links or path segment data records 1304, such as a link or path segment 1209, is generated from an open area map route. The link 1304 has two corresponding endpoints or nodes 1300, such as the nodes 1201 and/or 1205. The path segment 1304 represents a portion of a route that can be stored and retrieved when generating a navigation route. The nodes 1300 also can be stored and retrieved when generating the navigation route. The link or path segment record 1304 may also be associated with shape points 1308. The shape points or shape point attributes 1308 are used to represent a curve or curvature 1312 that represents that portion of the route in more detail rather than a simple line (e.g., the shape points identify a certain shape of a portion of a path represented by a link). For example, the shape points 1308 help reflect or identify a truer representation of the route portion by acting as guide points for curve fitting.

The generated data records are stored in the geographic or navigation database 1320, which may be the database 170 or a different database including hardware and/or software embodiments. The geographic database 1320 may be maintained by a map, geographic, and/or navigation data developer, such as NAVTEQ North America, LLC located in Chicago, Ill. The map developer collects geographic data to generate and enhance the database 1320. There are different ways used by the map developer to collect data. These ways include obtaining data from other sources, such as municipalities or respective geographic authorities. In addition, the map developer may employ field personnel to travel by vehicle along roads throughout the geographic region to observe features and/or record information about them. Also, remote sensing, such as aerial or satellite photography, may be used. Furthermore, the map developer may derive data records from open area maps.

The geographic database 1320 may be a master database stored in a format that facilitates updating, maintenance, and development. For example, the master geographic database 1320 or data in the master geographic database 1320 is in an Oracle spatial format or other spatial format, such as for development or production purposes. The Oracle spatial format or development/production database may be compiled into a delivery format, such as a GDF format. The data in the production and/or delivery formats may be compiled or further compiled to form geographic database products or databases, which may be used in end user navigation devices or systems.

For example, geographic data is compiled (such as into a PSF format) to organize and/or configure the data for performing navigation-related functions and/or services, such as route calculation, route guidance, map display, speed calculation, distance and travel time functions, and other functions, by a navigation device. The navigation-related functions may correspond to vehicle navigation, pedestrian navigation, or other types of navigation. The compilation to produce the compiled product databases may be performed by a party or entity separate from the map developer. For example, a customer of the map developer, such as a navigation device developer or other end user device developer, may perform compilation on a received geographic database in a delivery format to produce one or more compiled navigation databases.

The database 1320 includes node data records 1324, such as the records 1300, path segment data records 1328, such as the record 1304, POI records 1332, and an index 1336. Additional, fewer, or different components may be provided. For example, cartographic (“carto”) data records may be provided and other data records such as, but not limited to, routing data and maneuver data may also be included.

The path segment data records 1328 are links or segments representing portions of roads, streets, and/or paths (such as paths modeled or used in an open area). The path segment records 1328 may include shape point records 1340, such as the shape points 1308. The node data records 1324 are end points corresponding to the respective links or segments of the segment data records 1328. For example, the node data records may represent intersection points. The POI data records 1332 correspond to data or information regarding POIs, such as gasoline stations, hotels, restaurants, museums, stadiums, offices, automobile dealerships, auto repair shops, buildings, stores, fountains, indoor and/or outdoor structures, parks, lobbies, cafeterias, meeting spots, destinations, etc. The geographic database 1320 may include data about the locations of these POIs. The geographic database 1320 may also include data about places, such as cities, towns, or other communities, and other geographic features, such as bodies of water, mountain ranges, etc. Such place or feature data may be POI data or may be associated with POIs or POI data.

The nodes 1324 and/or shape points 1340 may be associated with node IDs or shape point IDs, respectively, by which the record can be identified in the geographic database 1320. The segments 1328 may be associated with segment IDs by which the record can be identified by the geographic database 1320. Also, the segment data records 1328 may also include data identifying the endpoints of the segments, the respective node records, and the location of the endpoints. Other data, such as field or category data or IDs, may be provided.

The path segment, node, POI, and/or other records may be associated with attributes, such as geographic coordinates (such as latitude, longitude, and/or altitude or other coordinates), other positioning information (such as local or indoor positioning data), street or path names or location or structure names, address ranges, speed limits, other speed or time information (such as average traverse time), turn restrictions (such as at intersections), other restrictions, and other navigation related attributes. For example, the nodes 1324 and/or shape points 1340 may be associated with coordinates or other position information. The links 1328 may be associated with distance or length information and/or speed or time information, such as an average time or other time is takes to traverse that particular segment. The POI records or POI attributes 1332 as well as other data records may be associated with the node data 1324 and the path segment data 1328 via the index 1336 and/or other means. The index 1336 may be one or more indexes or data structures that organizes and/or links the different data records with each other.

FIG. 14 illustrates a navigation device 1401 and a database 1425. For example, the device 1401 is an end user device, such as the device 116 or other device. The device 1401 includes, but is not limited to, a display 1405 and an input device 1409. Fewer, additional, or different components may be provided.

The display 1405 is any mechanical and/or electronic display positioned for accessible viewing in, on, or in communication with the device 1401. For example, the display 1405 is a touch screen, liquid crystal display (“LCD”), cathode ray tube (“CRT”) display, a plasma display, or other display. The display 1405 may act as a hardware implementation of a user interface or a portion thereof. The input device 1409 may be one or more buttons, keypad, keyboard, mouse, stylist pen, trackball, rocker switch, touch pad, voice recognition circuit, or other device or component for controlling or inputting data in one or more of the components of the device 1401.

The device 1401 is in communication with the database 1425. For example, the database 1425 is the geographic and/or navigation database 1320 or a similar database. Or, the database 1425 is a compiled database derived from the database 1320. The database 1425 may be external and/or remote to the device 1401 in which communication occurs over a wireless and/or wired network (such as in a server system). Alternatively, the database 1425 may be part of the device 1401. In one embodiment, an end user enables the device 1401 for routing purposes. For example, the end user wants to route from a current position or origin point 1417 to a destination 1421 within an indoor setting, an outdoor setting, or a combination thereof. The device 1401 generates a route 1413 by accessing path segment records (such as the data records 1328), node records (such as the node records 1324), and/or other data records in the database 1425 (e.g., when selecting the destination 1421, a POI record may have been accesses and/or retrieved). For example, based on a routing algorithm, different path segments and/or nodes are retrieved to create the path from point 1417 to point 1421. The route 1413 is then displayed on the display 1405. Accordingly, segment records, node records, and/or other records created from open area maps (as described above) are used for navigation functions. Routes or travel paths generated by open area map technology (such as mesh, grid, and/or tile associations) are modeled and stored for traditional link-node routing (i.e., for example, instead of using the open area map technology to route, nodes, links, and/or other data records are accessed (such as via a routing algorithm) to generate a route).

FIG. 15 is a flowchart of an exemplary method of generating geographic data. Fewer or more steps or acts may be provided, and a combination of steps may be provided. Also, the steps or acts may be performed in the order as shown or in a different order. The method is implemented by the system and/or devices described herein or by different devices or systems. One or more steps or processes of the method may be fully or partially automated (such as via a computer or algorithm). One or more steps may be implemented by the map developer or program thereof. Alternatively, one or more steps may be implemented by an end user and/or application or program on a user device (e.g., an end user device may include an application for converting open area maps into link-node maps).

In one embodiment, one or more open area maps, such as the map 1100, 601, and/or 700, is generated and/or identified (Step 1500). For example, the map developer creates an open area map or routable mesh map based on the disclosure above. The open area map is then identified by the map developer or other entity.

One or more routes are generated via the identified open area map (Step 1504). For example, the map developer or program generates some or all possible routes to some or all the destination points (e.g., different routes between possible combinations of routable points are generated). In one embodiment, POIs or destination points within an indoor and/or outdoor setting are routed to from respective origin points, such as illustrated by the routes 1104 and 1116. The routes are generated based on the mesh, tile, and/or open area map technology described above.

The one or more generated routes are used to create one or more node data records, such as the node records 1201, 1205, 1300, and/or 1324, (Step 1508). For example, the map developer or program determines or identifies points along the generated routes and designates them as nodes. The points or nodes correspond to intersection points between generated routes, intersections between path segments or links, starting or ending points, and/or other points.

One or more path segment or link data records, such as the link records 1209, 1304, and/or 1328, are created (Step 1512). For example, separate portions of a generated route are created by dividing the route into segments. This step can be an additional step relative to creation of the nodes. For example, this can occur before node creation or designation or the path segments can be identified separately after node creation. Alternatively, the creation of nodes may automatically or substantially at the same time create or identify the respective path segments. While or after creation or identification of the nodes and links, navigation attributes (such as coordinate or position information, time information, speed information, distance information, POI association, ID association, restrictions, etc.) are associated with the nodes and links. Also, shape points, such as the shape point records 1308 and/or 1340, are generated and/or associated with the path segments. Certain nodes may be identified or generated as POIs. For example, nodes representing destinations (such as an office, meeting point, park, etc.) may be kept track of and then designated as a POI at the end of a respective link. The POI records may be configured to be searched as routable destinations.

Furthermore, one or more other data records may be generated or created. Further description and details on node data records, segment data records, and/or other navigation data records or associated data may be provided in the United States patent, U.S. Pat. No. 6,038,559, entitled SEGMENT AGGREGATION IN A GEOGRAPHIC DATABASE AND METHODS FOR USE THEREOF IN A NAVIGATION APPLICATION, which is hereby incorporated by reference.

Nodes or node records may be clustered (Step 1516). For example, the size of a link-node graph or map based on the route generation above may be relatively large. To reduce the size, some nodes may be combined using one or more known or future clustering algorithms or techniques. In one embodiment, nodes within a certain area or boundary may be formed into one node, and other spatial criteria may be used. For example, a quality threshold algorithm may be used. Other algorithms, such as a k-means algorithm, may be used as well. Reducing the number of nodes via clustering can help in route calculation (smaller number of nodes may improve route processing), route display, and/or in other areas. Start and/or end nodes, which may represent destinations, may be excluded from the clustering process so that they are not moved. In one embodiment, the clustering process takes into consideration obstructions so that a node is not generated or moved in which a link passes through an obstruction or obstacle (e.g., a non-navigable or non-routable area). An appropriate cluster-size for a given map may be determined manually and/or automatically for the clustering process.

After clustering nodes, one or more links or segments that previously did not intersect may now cross or overlap each other. The map developer or other entity may repeat Steps 1508, 1512, and/or 1516 to create, determine, or identify new nodes, segments, and/or other data until the graph, map, or data records stabilize (Step 1520). Stabilization may be based on when there are no new nodes created by clustering or a threshold may be set, such as a threshold of N new nodes and/or links.

One or more node records may be converted to shape point records (Step 1524). For example, as part of the clustering process or in a different step or process, one or more nodes that may seem superfluous or correspond to a relatively small number of links may be changed into shape points, such as the shape points 1308 or 1340. Alternatively, any node may be changed into a shape point. This helps reduce the number of nodes and helps define the data model.

The generated and/or identified data records are stored in one or more geographic and/or navigation databases, such as the database 1320 or 1425 (Step 1528). For example, node data records (including reduced node data records), segment data records (including shape point records), POI records, and/or other records are stored in a database using known or future storage techniques. The data records may be associated or linked via one or more indexes, such as the index 1336. Accordingly, a link-node map and/or data records thereof derived from one or more open area maps or paths/routes thereof are stored and configured for navigation-related functions.

FIG. 16 is a flowchart of an exemplary method of routing. Fewer or more steps or acts may be provided, and a combination of steps may be provided. Also, the steps or acts may be performed in the order as shown or in a different order. The method is implemented by the system and/or devices described herein or by different devices or systems. One or more steps or processes of the method may be fully or partially automated (such as via a computer or algorithm).

A user, such as an end user, enables a device, such as the device 1401 (Step 1601). For example, a user turns on a device or application thereof for navigation purposes. The user wishes to route to one or more destinations using the device.

An origin is determined (Step 1605). For example, the current position of the device is determined via a GPS system, indoor positioning system, or other positioning system or method. Alternatively, the user selects or inputs an origin point, such as using an input device like the input device 1409.

A destination is determined (Step 1609). For example, the user selects a destination point by entering information of the destination, selecting a point on a screen, choosing from an option of destinations, and/or by other means.

A route is generated (Step 1613). For example, a route, such as the route 1413, between the origin and the destination is generated. In one embodiment, links and nodes as well as other data records that were created based on one or more open area maps or generated paths thereof are accessed when determining the route. Different path segments and/or nodes, such as the node data records 1324 and the path segment records 1328, as well as other data records from a database, such as the database 1320 or 1425, are retrieved. For example, different links are combined to form the route, and the segment records, node records, POI records, shape point records, and/or other records are taken into consideration for forming the route. For example, speed, time, distance, restriction, location or coordinate, and/or other information from or associated with the retrieved data records and/or other source(s), such as user preferences, are used to determine a route. Known or future routing algorithms may be used. A plurality of routes may be generated in this manner.

One or more generated routes are displayed (Step 1617). The route between the origin and destination is displayed on the device so that the user may view the route for navigation purposes and/or other purposes. Accordingly, a user may route in an area using a traditional link-node structure instead of or in addition to using an open area map, as described above.

The different steps, acts, or processes of the methods described herein may be mixed and matched. Also, other methods, such as a product-by-process method or process-by-process method, may be provided based on the disclosure herein. Furthermore, in an alternative embodiment, instead of or in addition to creating a link-node map or data from open area map generate routes, one or more link-node maps may be created from other maps or data structures, such as other indoor and/or outdoor navigation maps or data structures.

The logic, software, or instructions for implementing the processes, methods and/or techniques discussed above are provided on computer-readable storage media or memories or other tangible media, such as a cache, buffer, RAM, removable media, hard drive, other computer readable storage media, or any other tangible media. The tangible media include various types of volatile and nonvolatile storage media. The functions, acts, steps, or tasks illustrated in the figures or described herein are executed in response to one or more sets of logic or instructions stored in or on computer readable storage media. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firmware, micro code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like. In one embodiment, the instructions are stored on a removable media device for reading by local or remote systems. In other embodiments, the logic or instructions are stored in a remote location for transfer through a computer network or over telephone lines. In yet other embodiments, the logic or instructions are stored within a given computer, central processing unit (“CPU”), graphics processing unit (“GPU”) or system.

It is intended that the foregoing detailed description be regarded as illustrative rather than limiting and that it is understood that the following claims including all equivalents are intended to define the scope of the invention. 

I claim:
 1. A method of generating geographic data for navigation-related functions, the method comprising: obtaining a pre-existing image of a layout, the layout representing a real-world area in which a person moves about and wherein the pre-existing image include walls; using the pre-existing image to form a grid of contiguous tiles, wherein the grid has a shape that corresponds to a pedestrian-accessible contiguous sub-area within the real-world area and wherein the shape has a boundary that corresponds to the walls in the pre-existing image; generating a routable open area map as a function of the grid of contiguous tiles, wherein the routable open area map is configured to be displayed via an end user device; providing, via the end user device, an end user associated with the end user device with point-to-point routing within the routable open area map, wherein the point-to-point routing comprises calculating a route from one point corresponding to the pre-existing image to another point corresponding to the pre-existing image, the calculating of the route not being based on one or more path segments determined prior to the calculating; creating a path segment record representing a portion of the generated route; and storing the path segment record in a geographic database, the path segment record configured to be retrieved to form a navigation route.
 2. The method of claim 1, wherein the path segment record comprises a data representation of a link having two endpoints.
 3. The method of claim 2, wherein the two end points are each represented by respective node records.
 4. The method of claim 1, further comprising: determining a node record along the generated route by identifying an intersection between the calculated route and another calculated route.
 5. The method of claim 4, wherein the node record corresponds to an endpoint of the path segment record.
 6. The method of claim 4, further comprising: converting the node record to a shape point attribute that is associated with the path segment record.
 7. The method of claim 1, wherein the route from the one point to the other point comprises a route from an origin point to a destination point, and wherein the destination point is stored in the geographic database as a point-of-interest configured to be searched as a routable destination.
 8. The method of claim 1, wherein the pre-existing image of the layout comprises an image of a building floor plan.
 9. The method of claim 1, wherein the contiguous tiles are substantially uniform.
 10. A computer-readable medium including computer-executable instructions for performing a method of generating a link-node map for an area, the method comprising: overlaying an image of the area with a grid of tiles; associating each tile that overlays a navigable portion of the image with a property that permits travel to another tile immediately adjacent thereto that overlays another navigable portion of the image; generating a routable open area map as a function of the grid of tiles, the routable open area map configured to be displayed via an end user device; providing, via the end user device, an end user associated with the end user device with point-to-point routing within the routable open area map, wherein the point-to-point routing comprises calculating a plurality of routes between a plurality of points of the image, the calculating not being dependent upon one or more path segments determined prior to the calculating; creating node records that correspond to a plurality of points along the generated plurality of routes, wherein link data records are formed as segments having two node records as respective endpoints.
 11. The method of claim 10, wherein at least some of the plurality of points comprise intersection points between the calculated plurality of routes.
 12. The method of claim 10, further comprising: clustering the node records based on a spatial criteria; reducing a number of the node records by combining at least some of the node records into a single node record as a function of the clustering; and storing the reduced number of node records and the associated link data records in a navigation database.
 13. The method of claim 10, further comprising: converting at least some of the node records into shape point records corresponding to respective link data records, the shape point records identifying a certain shape of a portion of a path represented by the respective link data records.
 14. The method of claim 10, further comprising: for each of the points selected as a destination point when calculating the plurality of routes, generating a point-of-interest attribute; and storing each point-of-interest attribute in a navigation database.
 15. The method of claim 10, further comprising: designating a non-navigable property to tiles corresponding to an obstruction in the image.
 16. The method of claim 15, wherein the obstruction comprises a wall.
 17. A navigation database for generating a route from an origin to a destination, the navigation database created from a method of generating navigation data from an open area mesh map, the method comprising: identifying a routable map data structure including a grid of tiles corresponding to an image of an area, the tiles associated with navigable properties to generate routes from one portion of the grid associated with a point of the image to another portion of the grid associated with another point of the image, the routable map data structure configured to be displayed via an end user device; providing, via the end user device, an end user associated with the end user device with point-to-point routing within the routable map data structure, wherein the point-to-point routing comprises calculating a route from an origin to a destination based on the routable map data structure, the calculating not being based on one or more path segments determined prior to the calculating; creating node records corresponding to a plurality of points along the generated route; and storing the node records to form the navigation database, the node records configured to be retrieved to form a navigation route.
 18. The method of claim 17, further comprising: creating path segment records representing portions of the calculated route, the node records corresponding to respective endpoints of the path segment records; and storing the path segment records along with the node records to form the navigation database.
 19. A method of routing from an origin to a destination using a link-node map on a navigation device, the method comprising: receiving a selection input corresponding to a destination point; and generating a route from an origin point to the destination point, wherein generating the route includes retrieving a first path segment record from a geographic database; wherein the first path segment record is created from a method of generating navigation data from an open area mesh map comprising: obtaining a routable map data structure including a grid of tiles corresponding to an image of an area, the tiles associated with navigable properties allowing for point-to-point routing, the routable map data structure configured to generate a plurality of routes from any portion of the grid associated with a navigable point of the image to any other portion of the grid associated with another navigable point of the image, the routable map data structure configured to be displayed via an end user device; providing, via the end user device, an end user with point-to-point routing within the routable map data structure, wherein the point-to-point routing comprises calculating a route from a first point to a second point based on the routable map data structure, the calculating not being based on one or more path segments determined prior to the calculating; creating a plurality of path segment data records corresponding to a plurality of portions along the generated route, the plurality of path segment records including the first path segment record; and storing the plurality of path segment data records in the geographic database.
 20. A method of generating geographic data for navigation-related functions, the method comprising: identifying a routable map data structure including a grid of tiles corresponding to an image of an area, the tiles associated with navigable properties allowing for point-to-point routing, the routable map data structure configured to generate a plurality of routes from any portion of the grid associated with a navigable point of the image to any other portion of the grid associated with another navigable point of the image, the routable map data structure configured to be displayed via an end user device; providing, via the end user device, an end user associated with the end user device with point-to-point routing within the routable map data structure, wherein the point-to-point routing comprises calculating a route from an origin point to a destination point based on the routable map data structure, the calculating not being based upon one or more path segments determined prior to the calculating; creating path segment data records by dividing the generated route into a plurality of portions; and storing the path segment data records in a navigation database, the path segment data records configured to be retrieved to form a navigation route.
 21. The method of claim 20, wherein each path segment data record is associated with node data records, the node data records corresponding to endpoints of the path segment data records.
 22. The method of claim 20, wherein the routable map data structure does not include path segment records. 